@vacoo That type parameter will be inferred from the compiler. You can see working code here that's confirmed to be correct by the test suite:

https://github.com/riverqueue/river/blob/master/example_insert_and_work_test.go#L51

It looks like you've got a different problem somewhere. Your tooltip seems to be saying about NextRetry. Do you want to see if something weird is going on there?

@vacoo That type parameter will be inferred from the compiler. You can see working code here that's confirmed to be correct by the test suite:

https://github.com/riverqueue/river/blob/master/example_insert_and_work_test.go#L51

It looks like you've got a different problem somewhere. Your tooltip seems to be saying about NextRetry. Do you want to see if something weird is going on there?

The NextRetry method is already available in river.WorkerDefaults.

The NextRetry method is already available in river.WorkerDefaults.

Yep, I know. Are you sure you don't have any additional customization?

The NextRetry method is already available in river.WorkerDefaults.

Yep, I know. Are you sure you don't have any additional customization?

I don't think so. I use go land and go1.22.5 darwin/arm64

Hm, maybe check whether the code compiles outside Goland with go build .?

If that doesn't work, then maybe you could try copying the code from the example test just in case there's a typo or something somewhere:

https://github.com/riverqueue/river/blob/master/example_insert_and_work_test.go

Hm, maybe check whether the code compiles outside Goland with go build .?

If that doesn't work, then maybe you could try copying the code from the example test just in case there's a typo or something somewhere:

https://github.com/riverqueue/river/blob/master/example_insert_and_work_test.go

Strangely, everything works. It just seems to be just a warning

Ah weird. Possibly a GoLand issue somewhere ...